Add capabilities like reusing current symbol when renaming etc.

For rename symbol I think it would be more useful to prefill with the symbol to be renamed rather than the selection which feels more intuitive.

For rename symbol I think it would be more useful to prefill with the symbol to be renamed rather than the selection which feels more intuitive.

It's not easy to determine current symbol without talking with lsp server as it depends on the language.

There's a textDocument/prepareRename if the server supports it. https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_prepareRename

It will return the offsets of the string we're renaming: https://github.com/emacs-lsp/lsp-mode/blob/6157b3dde2c56f734a0789225240c521acdf2c7c/lsp-mode.el#L5849-L5871=

There's a textDocument/prepareRename if the server supports it. https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_prepareRename

It will return the offsets of the string we're renaming: https://github.com/emacs-lsp/lsp-mode/blob/6157b3dde2c56f734a0789225240c521acdf2c7c/lsp-mode.el#L5849-L5871=

Do we need below option too? This would make the case complex and I am not sure if I can handle this right now.

(defcustom lsp-rename-use-prepare t
Whether `lsp-rename' should do a prepareRename first.
For some language servers, textDocument/prepareRename might be
too slow, in which case this variable may be set to nil.
`lsp-rename' will then use `thing-at-point' `symbol' to determine
the symbol to rename at point."

I think it's okay to skip this for now and add a per LSP config option in the future if issues arise.